Service management system that enables subscriber-driven changes to service plans

ABSTRACT

A service management system that enables a subscriber of a mobile telecommunication system to modify aspects of his or her service plan and have the modification to the service plan take effect immediately. The subscriber enters a modification request to an aspect of a service plan. The modification request is verified against a set of rules that defines acceptable changes to the service plan. If the proposed modification to the service plan is a valid change, the change to the service plan is immediately propagated to a billing system and to other systems that implement the service plan. The subscriber is notified when the modification to the service plan is complete, and the subscriber is billed on a going-forward basis in accordance with the rate structure applicable to the plan.

TECHNICAL FIELD

The present invention relates to managing service plans in mobiletelecommunication systems.

BACKGROUND

Most consumers who use mobile telecommunication devices rarely changeaspects of their service plan with their mobile service provider. Thisrarity may be attributed to the time and effort required to effect theservice plan change. To make a change, a subscriber must typicallyinitiate contact with the service provider via a telephone call tocustomer service or via a self-help system on the service provider'swebsite. Once contact is initiated, implementing a change can be amulti-step process that takes a certain amount of time to complete and acertain understanding of all of the service plan options to make aninformed decision. While most service providers strive to simplify thisprocess, the change process may sometimes discourage subscribers frommaking a change to their service on a frequent basis.

Even if a service provider simplifies the process of changing aspects ofa subscriber's service plan, the process is often not performed in asubscriber-friendly fashion. Changes are rarely implemented immediately,and may take twenty-four (24) hours or more to propagate through theservice provider's systems. While most consumers are willing to acceptthis delay, the lack of immediate feedback to the consumer is asub-optimal experience. Most consumers would prefer a service providerthat reduces the time and effort necessary to change a service plan,such as by eliminating the need to personally contact the serviceprovider. Most consumers would also prefer a service provider thatcompleted a requested change immediately. If such an offering existed,it is expected that subscribers would more frequently make changes totheir service plan and would ultimately be more satisfied with theservice that they receive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating components of a telecommunicationsystem that enables subscriber-driven changes to a service plan.

FIG. 2 is a block diagram illustrating aspects of a service plan storedin a mobile device of a subscriber.

FIG. 3 is a block diagram illustrating components of a servicemanagement system.

FIG. 4 is a block diagram illustrating records in a subscriber databaseaccessed by the service management system.

FIGS. 5A and 5B are flow diagrams illustrating the processing of arequest by a subscriber to modify an aspect of his or her service plan.

DETAILED DESCRIPTION

A service management system is disclosed that enables a subscriber of amobile telecommunication system to modify aspects of his or her serviceplan and have the modification to the service plan take effectimmediately. The subscriber effects changes to his or her service planvia a mobile device interface or via a non-mobile computer interface.The subscriber directly enters a modification to an aspect of the plan.The subscriber's proposed modification is verified against a set ofrules that defines acceptable changes to the service plan. If theproposed modification to the service plan is a valid change, the changeis immediately propagated to a billing system and to other systems thatimplement the service plan. The subscriber is notified when themodification to the service plan is complete, and the subscriber isbilled on a going-forward basis in accordance with the rate structureapplicable to the plan. Subscribers benefit under the system becausechanges are easily made by the subscriber and implemented in a timelyfashion. As a result, overall subscriber satisfaction with the serviceprovider is enhanced.

In some embodiments of the system, the provider's service plan allowssubscribers to create a contact group containing a limited number ofpeople or services. Communications to and/or from the people or servicesin the contact group are billed at a reduced rate (e.g., allcommunications are free, all communications are billed at a fixedmonthly fee, all communications are billed at a reduced rate). Thesubscriber is allowed to periodically change the members of the contactgroup, with the service plan's billing scheme being applied to the newmembers in the contact group as soon as any change is made. Certainrules are applied to the composition of the contact group, including theallowed frequency of updates to the group, thereby constraining some ofthe modifications that the subscriber can make to the group. Anymodifications to the service plan proposed by the subscriber aretherefore verified by the service management system against a set ofrules that characterize acceptable changes before being implemented.

The terminology used in the description presented below is intended tobe interpreted in its broadest reasonable manner, even though it isbeing used in conjunction with a detailed description of certainspecific embodiments of the invention. Certain terms may even beemphasized below; however, any terminology intended to be interpreted inany restricted manner will be overtly and specifically defined as suchin this Detailed Description section.

Various embodiments of the invention will now be described. Thefollowing description provides specific details for a thoroughunderstanding and enabling description of these embodiments. One skilledin the art will understand, however, that the invention may be practicedwithout many of these details. Additionally, some well-known structuresor functions may not be shown or described in detail, so as to avoidunnecessarily obscuring the relevant description of the variousembodiments.

FIG. 1 is a block diagram illustrating some of the components of amobile telecommunication system 100 that includes a service managementsystem 110 that allows subscribers to manage aspects of a service planoffered by a service provider in substantially real-time. The servicemanagement system 110 acts as an intermediary between a population ofsubscribers using mobile devices 120, a billing system 130, and acommunication network 140 that enable the subscribers to receive mobiletelecommunications services in exchange for a fee. Mobile devices 120may include mobile phones, mobile personal digital assistants (e.g.,Palms, PocketPCs, Blackberries or Treos), or any other mobile devicehaving a service plan. The mobile devices 120 may each contain a serviceclient 180 that in conjunction with the service management system 110allows a subscriber to manage aspects of his or her service plan.

For purposes of this description, a group-centric service plan is usedas a representative service plan managed by the subscriber. In agroup-centric plan, a subscriber is allowed to define a set of contactnumbers in a contact group. A contact number can represent either aperson or a service, for example, a service that receives emailed imagesand automatically prints the received image. Communications made betweenthe subscriber and any of the contact numbers in the contact group arebilled at a different rate than communications with contact numbers thatare not in the contact group. For example, the subscriber may be billedat a flat rate for all communications with members in the contact group,at a discount for each communication with members in the group, or allcommunications with members in the group might be free. Alternatively,communications made between the subscriber and any of the contactnumbers in the contact group may be provided with preferential serviceor a feature that is not accessible to communications with contactnumbers that are not in the contact group. For example, the subscribermay be provided with the ability to simultaneously broadcast the samemessage to members of his or her contact group, but not to membersoutside of his or her contact group. As another example, the subscribermay be provided with special ringtones for members of his or her contactgroup. In this context, “communication” means the transmission orreceipt by the subscriber of any voice call, text, SMS message, instantmessage, email, picture, music, or any other data. The size of thecontact group may vary significantly, but often the group containstwenty or less contact numbers. Moreover, members of the group can beassociated with any telecommunication network, whether wired orwireless. That is, the contact numbers do not necessarily representpeople or services that are serviced by the same mobiletelecommunication system 100 as the subscriber. Additional informationabout a group-centric service plan is described in greater detail inU.S. patent application Ser. No. ______ (Attorney Docket Number50123.06USU1), entitled “Preferred Contact Group Centric Interface,”filed on 10 Apr. 2006 and incorporated in its entirety by thisreference. While a group-centric service plan is used as arepresentative service plan throughout this description, it will beappreciated that the technology described herein is applicable to manyother types of service plans as well. The described system is intendedto apply to any service plan that would benefit from allowing asubscriber to make periodic modifications to the service plan, whereinthe modifications are immediately implemented.

As shown in FIG. 1, the service management system 110 may communicatewith mobile devices through a number of different communication paths.In the depicted embodiment, two communication paths are shown. The firstpath allows the mobile devices 120 to communicate with the servicemanagement system 110 through a WAP (Wireless Application Protocol)server 150. Those skilled in the art will appreciate that the WAPprotocol enables mobile devices to access WAP-enabled websites andexchange information such as World Wide Web content using the hyper-texttransfer protocol (HTTP). The second path allows the mobile devices 120to communicate with the service management system 110 through a shortmessage service (SMS) center 160. Those skilled in the art willappreciate that the SMS center stores and forwards SMS messages betweenthe mobile devices and the service management system using the shortmessaging service peer-to-peer protocol (SMPP).

The service management system 110 also communicates with othercomponents of the mobile telecommunications system 100 such as thebilling system 130 and the communication network 140. The billing system130 is an industry-standard billing system that bills for allcommunications made by a subscriber of a mobile device 120 during abilling period. The billing system includes a database 170 thatmaintains accurate and complete records of all billed uses of thetelecommunication system 100 for each subscriber. The communicationnetwork 140 broadly encompasses all of the other systems in thetelecommunication system that enables a mobile subscriber to haveend-to-end connectivity with other people or services. The servicemanagement system 110 is also connected to the World Wide Web 190 asnecessary to implement the functionality described herein. Those skilledin the art will appreciate that other standard systems and connectionshave been omitted from the mobile telecommunications system 100 forclarity.

Mobile devices 120 may include a service client 180 that uniquelyidentifies the subscriber and interfaces with the subscriber managementsystem 110. The service client 180 maintains a record of certainsubscriber-modifiable elements of the service plan. For example, in anembodiment wherein the service plan is a group-centric service plan, theservice client 180 includes a table that identifies all of the contactsin a contact group. FIG. 2 is a representative service plan table 195that is maintained by the service client 180. The table includes anumber of fields that pertain to the service plan, including: a MobileSubscriber ISDN Number field 200, which contains a number that uniquelyidentifies the subscriber to the service provider; an allowed contactsfield 205, which contains a number that sets the size of (i.e., thenumber of contacts in) the contact group; and group contact fields 210a, 210 b, . . . 210 e. Each group contact fields 210 a, 210 b, . . . 210e identifies a contact by contact number and by subscriber-defined name.The contact number may be a phone number, an IP address, or any uniqueidentifier that can be used to complete a communication with anotherperson or service. The format of the contact number andsubscriber-defined name may vary, but in an embodiment of the systemseventeen digits are provided for the contact number and sixteen digitsare provided for the subscriber-defined name. The service plan table 195is maintained by the service client 180, and modifications to theservice plan table are made in accordance with the process describedbelow.

Prior to managing his or her service plan, a subscriber may firstcontact his or her service provider in order to activate the serviceplan. Contact with the service provider may be made in a variety ofways, including using the mobile device to send an SMS message to theprovider or to visit a WAP webpage offered by the provider.Alternatively, the subscriber may contact the service provider byvisiting the service provider's website using a laptop or desktopcomputer, by calling the service provider's customer service, or byvisiting any of the service provider's retail stores and interactingwith a sales person. After the service provider confirms that thesubscriber is eligible to participate in the service plan, the servicemanagement system 110 and the service client 180 are each provisioned toconfigure the subscriber for service. In the case of the mobile device,the service management system 110 sends a command to the service client180 turning the client “on.” At this point, the subscriber is allowed tobegin managing aspects of his or her service plan and makingmodifications to certain aspects of the plan.

If the subscriber has activated a group-centric service plan, one of theaspects of the plan that the subscriber is allowed to manage is thecomposition of the contact group. When the service management systemactivates a group-centric plan it may populate all of the group contactfields 210 a, 210 b, . . . 210 e in the service client 180 with zeros asan initial state, signifying that the subscriber has no contacts. Afteractivation, the subscriber is allowed to populate the contact group witha desired group of people or services and manage the composition of thegroup over time. Information about the user interface that may beincorporated in the mobile device 120 to allow subscribers to modify thecomposition of their contact group is described in greater detail in thepreviously-referenced U.S. Patent Application entitled “PreferredContact Group Centric Interface.” The subscriber is allowed to add newcontacts into his or her contact group, change the contact number orcontact name of existing contacts, and delete contacts from his or hercontact group by making a modification request to the service managementsystem 110. The modification request may be generated by the subscriberusing the subscriber's mobile device (e.g., via an SMS message or WAPpage) or by accessing the service provider's website using a non-mobilecomputing device. In an embodiment, the modification request issubmitted to the service management system 110 in the following form:

[command] [position number] [contact number] [contact name]     e.g.,modify 02 4255551616 AliceWhere [command] is the desired command, [position number] is thenumerical position of the contact within the contact group that is to bemodified, and [contact number] and [contact name] are the contactdetails entered by the subscriber. In the example modification requestmade above, the subscriber is requesting that the second contact(position 02) in the contact group be modified so that the contactnumber is “425-555-1616” and the name is “Alice.” In an embodiment ofthe system, the command field is a two digit code, with each combinationof digits representing a different command (e.g., modify=“01”). Variousother commands may therefore be supported by the system, as will bedescribed in additional detail below.

FIG. 3 is a block diagram illustrating the various components of theservice management system 110 that receives the modification request andallows a subscriber to change an aspect of his or her service plan sothat the changes are immediately implemented and reflected in how thesubscriber is billed. As will be described in greater detail below, theservice management system includes a service rule set 220 that definesthose conditions under which the subscribers may modify their serviceplan. The service management system includes a subscriber database 215that contains details about subscriber service plans, including thoseaspects of the service plan that may be manipulated by a subscriber.When the service plan is the group-centric plan described above, thesubscriber database stores the identity of the people or servicescontained in the subscriber's contact group. FIG. 4 is a representativetable 300 of the type of information that may be stored in the databasefor a group-centric plan.

As depicted in FIG. 4, each record 310 in the table 300 represents onesubscriber and the identity of all contacts that the subscribermaintains in his or her contact group. Each record 310 contains a numberof fields, including: a Mobile Subscriber ISDN Number field 320, a timestamp field 330, an allowed contacts field 340, an account type field350, and a number of group contact fields 360 a, 360 b, . . . 360 n. TheMobile Subscriber ISDN Number field 320 contains a number that uniquelyidentifies the subscriber for the service provider. In the sample record370, the number is the 15 digit code “968375100064721.” The time stampfield 330 contains a timestamp that indicates when the subscriber wasfirst provisioned with the service plan. The allowed contacts field 340contains a number that is set by the service provider to reflect themaximum number of contacts that the subscriber may have in his or hercontact group. In the sample record 370, the number of contacts is setfor five. The account type field 350 contains a code number reflectingthe type of account that the subscriber maintains with the serviceprovider. For each person in a subscriber's contact group, the groupcontact fields 360 a, 360 b, . . . 360 n contain a contact number 375, asubscriber-defined name 380 of the contact, and a service provider code385. The contact number may be a phone number, an IP address, or anyunique identifier that can be used to complete a communication withanother person or service. The format of the contact number andsubscriber-defined name may vary, but in an embodiment of the systemseventeen digits are provided for the contact number and sixteen digitsare provided for the subscriber-defined name. The service provider codeis a code that identifies the service provider that the contact isassociated with. As was previously described, the service plan mayinclude communications between the subscriber and people or services inother service networks, so the service provider code is stored to bothtrack the number of contacts that are in other networks as well asfacilitate communication with those networks. It will be appreciatedthat the order of contacts in the database record 310 may correspond tothe order of contacts in the display provided to the subscriber on themobile device. For example, in record 370 the first contact isidentified as “Uncle Scott” and the fifth contact is identified as“Mom.” These contacts would be displayed in the first and fifthlocations, respectfully, on the mobile device. The contact numbers forUncle Scott and Mom are provided, and it is noted that Uncle Scott andMom use different service providers than the subscriber. When asubscriber first activates his or her service plan, the subscriberrecord 310 is populated with details of the service plan and zeros inall group contact fields 360 a, 360 b, . . . 360 n. For example, record390 represents a new subscriber that has recently activated thegroup-centric service plan. Record 395 represents a subscriber that hasactivated a group-centric service plan, but has not yet populated all ofthe contacts in the contact group as evidenced by the zeros in groupcontract field 360 n.

While FIGS. 2 and 4 depict a table whose contents and organization aredesigned to make them more comprehensible to the human reader, thoseskilled in the art will appreciate that the actual data structure(s)used by the system to store this information may differ from the tablesshown, in that they, for example, may be organized in a differentmanner, may contain more or less information than shown, may becompressed and/or encrypted, and may be optimized in a variety of ways.

Returning to FIG. 3, when a modification request is received by theservice management system 110 it is acted on in substantially real-timeto either implement the modification request or to reject themodification request if it fails to satisfy the rules that governallowed modifications. A process implemented by the service managementsystem 110 to implement or reject the modification request is depictedin FIGS. 5A and 5B.

FIGS. 5A and 5B are flow charts that illustrate portions of a process400 implemented by the service management system 110 to allowsubscribers to manage an aspect of their service plan. The flow chartdepicted in FIGS. 5A and 5B is suitable for a group-centric serviceplan, but may be modified as appropriate for other types of serviceplans. At a block 405, a request is received from a subscriber to modifyone of the contacts in his or her contact group. As was previouslydiscussed, the modification request is received in the following form:[command] [position number] [contact number] [contact name], where[command] is the command to modify, [position number] is the numericalposition of the contact within the contact group that is to be modified,and [contact number] and [contact name] are the contact details enteredby the subscriber. Note that the modify command can be used to representa number of different subscriber requests such as adding a contact tothe contact group, deleting a contact from the contact group, orchanging the position number, contact number or contact name of acontact. For example, deleting a contact may involve inserting all zerosin the corresponding record. Those skilled in the art will appreciatethat commands other than “modify” may also be used to manipulate entrieswithin the contact group.

At a block 410, the service management system determines if thesubscriber has activated the service plan that the subscriber is seekingto modify. If the subscriber has not activated the service plan, at ablock 415 the subscriber is redirected to a service sign-up page. Theservice sign-up page may be communicated to the subscriber using an SMSmessage, web-page redirect, or by other contact method. Afterredirecting the subscriber, the process terminates pending thesubscriber activating the service.

If the subscriber has activated the service plan that he or she isseeking to modify, at a decision block 420 the service management systemdetermines whether the modification request entails only a name change.Modification requests that entail only a name change may be processedwith less scrutiny by the system, as the decision of what name toassociate with a contact number in the service plan is entirely withinthe discretion of the subscriber. One way to determine if only a namechange has been requested is to compare the request with the associatedsubscriber record in the subscriber database 215. If only a name changeis required, at a block 425 the service management system sends acommand updating the name to the service client 180 in the subscriber'smobile device 120. The service management system also updates thesubscriber record in the subscriber database 215 to reflect the new namefor the identified contact. It will be appreciated that the definitiverecord of the subscriber's contact group is maintained in the subscriberdatabase 215 by the service management system 110, and that anymodifications to the record are made both locally in the servicemanagement system 110 and remotely at the subscriber's mobile device120. At a block 430, the service management system sends a message tothe subscriber confirming that the modification request has beencompleted. Once the modification request has been acted on, processingof the request is complete.

If the modification request entails more than a change to a contactname, processing continues to decision block 435. At decision block 435,the service management system performs a test to determine whether thereceived contact number in the modification request is a valid contactnumber. Different rules may be applied to determine that a contactnumber is valid, but in an embodiment of the system a contact number isconsidered to be valid if it falls within a certain geography (e.g.,within the continental United States) and does not fall on the list ofcertain numbers that should be excluded (e.g., due to past problems withfraud on an excluded number). If the contact number is found not to be avalid number, at a block 440 the service management system sends acommand to the service client 180 rejecting the modification request.When the service client 180 receives the command rejecting the request,the modification request is discarded and no changes are made to thecontact group maintained in the service client 180. At a block 445, theservice management system sends a message to the subscriber indicatingthat the entered contact number is not a valid number and thatprocessing of the modification request has been halted. An option may begiven to the subscriber to re-enter or otherwise correct the contactnumber. If such an option is provided, processing of the modificationrequest would begin again at block 405.

If the contact number is found to be a valid number at decision block435, processing continues to a block 450. At block 450, one of aplurality of service rules may be applied to the modification request.Service rules are defined by the service provider to set limits on whatactions a subscriber may take in changing aspects of his or her serviceplan. For example, in some embodiments of the system the serviceprovider may set a rule that each contact in the contact group cannot bemodified more than once a month or once every X days. In otherembodiments, a rule may be set that a subscriber can only make a certainnumber of modifications a month (e.g., five). Subscribers may thereforedecide whether to change one contact multiple times or multiple contactsone (or more) times. The service rules are stored in the service ruleset 220, and accessed by the service management system 110. At adecision block 455, the service management system performs a test todetermine whether the modification request satisfies the applied servicerule. If the modification request satisfies the service rule, processingcontinues to a decision block 460 where the service management systemdetermines whether there are additional service rules to apply. Ifadditional rules need to be applied, processing returns to block 450 toapply the next service rule. If no additional rules need to be applied(and by implication, all previous service rules have been satisfied),processing continues to a block 475. It will be appreciated that thenumber of service rules is in the discretion of the service provider,and may range anywhere from zero (i.e., no rules are applied) to a largenumber of interdependent rules that would require more complexprocessing to determine whether they are satisfied.

If the modification request fails to satisfy any of the applied servicerules at decision block 455, processing continues to a block 465. Atblock 465 the service management system sends a command to the serviceclient 180 rejecting the modification request. When the service client180 receives the command rejecting the request, the modification requestis discarded and no changes are made to the contact group maintained inthe service client 180. At a block 470, the service management systemsends a message to the subscriber indicating that the modificationrequest will not be made because the request failed to satisfy one ofthe service rules. Additional details about why the request failed mayalso be provided to the subscriber in the message. Once the modificationrequest has been rejected, further processing is terminated.

Returning to block 475, the modification request may be acted upon sincethe modification request has satisfied all of the service rules andother tests. At block 475, the service management system 110 makes theappropriate modification to the subscriber database 215 by updating thecontents of the subscriber's record. In the example modification requestpresented above, this would entail changing the second contact in thecontact group to the contact number “425-555-1616” and the name “Alice.”At block 480, the service management system 110 sends a modificationrequest to the billing system 130. Those skilled in the art willappreciate that the billing system maintains its own database 170 ofsubscribers and subscriber contact groups so that it may appropriatelybill the subscriber for services used under that service plan. It isbeneficial to update the billing system in substantially real-time asdoing so enables ongoing reconciliation between the networks ofdifferent service providers. At a block 485, the service managementsystem 110 waits to receive confirmation from the billing system thatthe modification has been made. When such confirmation is received, at ablock 490, the service management system sends a command to the serviceclient 180 directing the service client to implement the modificationrequest. At a block 495, the service management system sends a messageto the subscriber confirming that the modification request has beencompleted. Once the modification request has been acted on, processingof the request is complete.

Returning to FIG. 3, in addition to managing the proposed modificationto the service plan by a subscriber, the service management system 110may also manage other aspects of the activation, deactivation, andmaintenance of a subscriber. As was previously mentioned, the servicemanagement system 110 may send an “on” command to the service client 180to activate the client in anticipation of providing service. In additionto the “on” command, the service management system 110 may also send an“off” command to the service client 180 to deactivate the client.Deactivation may occur at the request of the subscriber, such as whenthe subscriber cancels a service, or may occur at the direction of theservice provider when the subscriber fails to pay for a service orotherwise violates the terms of use of a service. The service managementsystem 110 may also implement a “sync” command that is received from theservice client 180. The sync command causes the service managementsystem to copy the relevant contents from the subscriber's record 310 inthe subscriber database 215 to the service plan table 195 maintained bythe service client 180. The sync command may be used when a subscriberswitches to a new mobile device or otherwise needs to update thecontents of the entire contact group.

The service management system 110 also includes a number of componentsthat allow the service provider to manage the system and allow themanagement system to communicate with the other portions of thetelecommunication system. The service management system 110 includesinterfaces 230, an alarm management and rollover control component 240,a reporting and analytics component 250, and an operating systemcomponent 260. The interfaces 230 are provided to allow the servicemanagement system 110 to communicate with other systems in thetelecommunication system 100, such as the billing system 130 and thecommunication network 140. The interfaces may operate using a variety ofstandard protocols or defined APIs, such as SOAP or XML forcommunication with the billing system.

The alarm management and rollover control component 240 is included inthe service management system 110 to maintain the overall reliability ofthe service management system. It will be appreciated that becausemodifications to subscriber service plans are intended to occur in amanner that is substantially in real-time, the service management system110 is preferably a highly reliable service. In order to reach thisgoal, various technological solutions may be implemented. For example,the service management system may operate on a number ofgeographically-dispersed servers that are configured to be redundant. Inthe event that one of the servers fails, the other servers may take overthe load without interruption of service. Alternatively, a standbyserver may be maintained that can be hot-swapped into the system in theevent that a primary server fails. Those skilled in the art willappreciate that other solutions to maintain high reliability may beimplemented by the alarm management and rollover control component 240.

The reporting and analytics component 250 allows the service providerthat operates the service management system 110 to compile and review anumber of reports that detail the health and operation of the system andthe service plan. For example, when the service plan is a group-centricplan, the reporting and analytics component may produce reports such asthe average number of subscribers, the average number of groupmodifications segmented in certain time periods (e.g., daily, weekly,monthly, yearly), the average number of group modifications rejected bythe system, etc. Reports generated by the reporting and analyticscomponent 250 allow the service provider to appropriately provisionresources for the service management system, tailor the service planbased on the actual use of the subscriber base, and in general reviewsystem operation to ensure a high degree of subscriber satisfaction.

The operating system component 260 is one or more operating systems thatcreate the environment for the operation of the software applicationsand database within the service management system. Those skilled in theart will appreciate that other standard components may be included inthe service management system 110 in order to achieve the functionalitydescribed herein.

It will be appreciated that the system configuration disclosed hereinsignificantly improves subscriber experience. Subscribers are able tomodify aspects of his or her service plan in a variety of ways, and themodifications are quickly propagated throughout the telecommunicationsystem so that the subscriber begins operating under the modified planin a very short period (often in a few minutes or less). Billingintegrity is maintained as changes are made to the billing system soonafter the subscriber makes the modification request.

While various embodiments are described in terms of the environmentdescribed above, those skilled in the art will appreciate that variousmodifications can be made to the system without impacting the overallfunctionality. For example, while a service client 180 is maintained onthe mobile device to ensure that the subscriber may view his or hergroup contacts even when not in range of a service network, a systemcould be envisioned that would only maintain the group contacts at acentral server. A subscriber would access the central server to makemodifications as described herein.

It will also be appreciated that the system may be implemented in avariety of environments. For example, the system could be implementedusing a single monolithic computer system, a distributed system, orvarious other combination of computer systems or similar devicesconnected in a variety of ways. The system could be implemented usingthird-party services and data for all or portions of the aforementionedfunctionality. Moreover, as used herein, the term “database” should beinterpreted to include any data structure that allows data to be storedand accessed, such as tables, linked lists, flat files, arrays, etc.Those skilled in the art will also appreciate that the steps shown inFIGS. 5A and 5B may be altered in a variety of ways. For example, theorder of the steps may be rearranged, substeps may be performed inparallel, steps may be omitted, or other steps may be included.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or,” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

From the foregoing, it will be appreciated that specific embodiments ofthe invention have been described herein for purposes of illustration,but that various modifications may be made without deviating from thespirit and scope of the invention. Accordingly, the invention is notlimited except as by the appended claims.

1. A method of enabling a subscriber to modify a service plan for amobile device so that the subscriber is billed in accordance with themodified service plan, the method comprising: (a) receiving a requestfrom a mobile device of a subscriber to modify a service plan for themobile device; (b) verifying that the received request is a validmodification request; and (c) if the received request is a validmodification request, updating the service plan in accordance with thereceived request so that the subscriber is billed in accordance with themodified service plan, wherein the update to the service plan isperformed in substantially real-time.
 2. The method of claim 1, whereinthe request from the mobile device is received via an SMS message. 3.The method of claim 1, wherein the request from the mobile device isreceived via a WAP page.
 4. The method of claim 1, wherein verifyingthat the received request is a valid modification request comprisescomparing the received request with one or more rules.
 5. The method ofclaim 1, wherein verifying that the received request is a validmodification request comprises confirming that the service plan has beenactivated for the mobile device.
 6. The method of claim 1, whereinverifying that the received request is a valid modification requestcomprises confirming that the received request provides accurateinformation.
 7. The method of claim 1, wherein updating the service plancomprises modifying a record associated with the subscriber in a billingsystem to change how the subscriber is billed for the service plan. 8.The method of claim 7, further comprising communicating to a subscriberthat the update to the service plan has been completed after the recordassociated with the subscriber in the billing system has been modified.9. The method of claim 1, wherein updating the service plan comprisesmodifying a record containing information about the subscriber.
 10. Themethod of claim 1, wherein the service plan is applicable to a pluralityof mobile devices.
 11. The method of claim 1, further comprisingcommunicating to the subscriber that the update to the service plan hasbeen completed.
 12. A system for enabling a subscriber to modify aservice plan for a mobile device so that the subscriber is billed inaccordance with the modified service plan, the system comprising: averification component that receives a request to modify a service planfrom a mobile device of a subscriber and verifies that the receivedrequest is a valid modification request; and a service managementcomponent that, upon receiving verification from the verificationcomponent that the received request is a valid modification request,updates the service plan associated with the mobile device of thesubscriber in accordance with the modification request so that thesubscriber is billed in accordance with the modified service plan,wherein the update to the service plan is performed in substantiallyreal-time.
 13. The system of claim 12, wherein the request to modify theservice plan from the mobile device is received via an SMS message. 14.The system of claim 12, wherein the request to modify the service planfrom the mobile device is received via a WAP page.
 15. The system ofclaim 12, wherein the verification component verifies that the receivedrequest is a valid modification request by comparing the receivedrequest with one or more rules.
 16. The system of claim 12, wherein theverification component verifies that the received request is a validmodification request by confirming that the service plan has beenactivated for the mobile device.
 17. The system of claim 12, wherein theverification component verifies that the received request is a validmodification request by confirming that the received request providesaccurate information.
 18. The system of claim 12, wherein the servicemanagement component updates the service plan by modifying a recordassociated with the subscriber in a billing system to change how thesubscriber is billed for the service plan.
 19. The system of claim 18,further comprising a communication component that notifies thesubscriber that the update to the service plan has been completed,wherein the subscriber is notified after the record associated with thesubscriber in a billing system is modified.
 20. The system of claim 12,wherein the service management component updates the service plan bymodifying a record containing information about the subscriber.
 21. Thesystem of claim 12, wherein the service plan is applicable to aplurality of mobile devices.
 22. The system of claim 12, furthercomprising a communication component that notifies the subscriber thatthe update to the service plan has been completed.
 23. In a mobiletelecommunication system, a method of enabling a subscriber to modify agroup of contacts associated with a mobile device so that communicationswith members in the group of contacts receive a different treatment thancommunications with members that are not in the group of contacts, themethod comprising: (a) receiving a request from a subscriber to modifyone of a group of contacts associated with a mobile device; (b)verifying that the received request is a valid modification request; and(c) if the received request is a valid modification request, modifying atreatment associated with the one of the group of contacts, whereinsubsequent service associated with the one of the group of contacts isprovided in accordance with the modified treatment such that members inthe group of contacts receive a different treatment than communicationswith members that are not in the group of contacts.
 24. The method ofclaim 23, wherein the request from the subscriber is received via an SMSmessage.
 25. The method of claim 23, wherein the request from thesubscriber is received via a WAP page.
 26. The method of claim 23,wherein the request from the subscriber is received via a web page. 27.The method of claim 23, wherein the treatment is a billing rate.
 28. Themethod of claim 23, wherein the treatment is a feature.
 29. The methodof claim 23, wherein the treatment is preferential service.
 30. Themethod of claim 23, wherein verifying that the received request is avalid modification request comprises comparing the received request witha rule.
 31. The method of claim 30, wherein the rule sets a limit on thenumber of modifications that can be made to the group of contacts withina time period.
 32. The method of claim 30, wherein the rule sets a limiton the number of modifications that can be made to one of the group ofcontacts within a time period.
 33. The method of claim 30, wherein therule sets a limit on the number of modifications that can be made to asubset of the group of contacts within a time period.
 34. The method ofclaim 23, wherein verifying that the received request is a validmodification request comprises verifying that the received requestprovides accurate information.
 35. The method of claim 23, furthercomprising communicating to a subscriber that the modification requesthas been completed after the modification to the treatment has beenperformed.
 36. The method of claim 23, wherein the modification to thetreatment is performed in substantially real-time.
 37. The method ofclaim 23, further comprising communicating to the subscriber that themodification request has been completed.
 38. The method of claim 23,wherein the group of contacts is applicable to a plurality of mobiledevices.
 39. A system for enabling a subscriber to modify a group ofcontacts associated with a mobile device so that communications withmembers in the group of contacts receive a different treatment thancommunications with members that are not in the group of contacts, thesystem comprising: a verification component that receives a request froma subscriber to modify one of a group of contacts and verifies that thereceived request is a valid modification request; and a servicemanagement component that, upon receiving verification from theverification component that the received request is a valid modificationrequest, modifies a treatment associated with the one of the group ofcontacts.
 40. The system of claim 39, wherein the request from thesubscriber is received via an SMS message.
 41. The system of claim 39,wherein the request from the subscriber is received via a WAP page. 42.The system of claim 39, wherein the request from the subscriber isreceived via a web page.
 43. The system of claim 39, wherein thetreatment is a billing rate.
 44. The system of claim 39, wherein thetreatment is a feature.
 45. The system of claim 39, wherein thetreatment is a preferred service.
 46. The system of claim 39, whereinthe verification component verifies that the received request is a validmodification request by comparing the received request with a rule. 47.The system of claim 46, wherein the rule sets a limit on the number ofmodifications that can be made to the group of contacts within a timeperiod.
 48. The system of claim 46, wherein the rule sets a limit on thenumber of modifications that can be made to one of the group of contactswithin a time period.
 49. The system of claim 46, wherein the rule setsa limit on the number of modifications that can be made to a subset ofthe group of contacts within a time period.
 50. The system of claim 39,wherein the verification component verifies that the received request isa valid modification request by verifying that the received requestprovides accurate information.
 51. The system of claim 39, wherein theservice management component further modifies a service plan associatedwith the one of the group of contacts.
 52. The system of claim 39,wherein the update to the treatment associated with the one of the groupof contacts is performed in substantially real-time.
 53. The system ofclaim 39, further comprising a communication component that communicatesto the subscriber that the modification request has been completed. 54.The system of claim 39, wherein the group of contacts is applicable to aplurality of mobile devices.
 55. One or more propagated data signalscollectively conveying a modification request to a group of contactsassociated with a mobile device of a subscriber of a telecommunicationsystem, the one or more propagated data signals comprising: a commandsegment specifying that a modification is to be made to one contact of agroup of contacts associated with a mobile device of a subscriber; and adata segment specifying a modified contact number associated with theone contact of the group of contacts, wherein the modification that ismade to the contact number results in a different billing rate beingapplied to communications with the contact number via the mobile device.56. The one or more propagated data signals of claim 55, furthercomprising a second data segment specifying a contact name associatedwith the one contact of the group of contacts.
 57. The one or morepropagated data signals of claim 55, further comprising a third datasegment specifying a list position of the one contact in the group ofcontacts.